Adaptively strengthening ecc for solid state cache

ABSTRACT

In an aspect of the subject matter, a “full” amount of the flash cache (e.g., storage cells) is initially utilized to store data i.e., substantially all of the storage space of the flash cache may be designated to store user data, with the remaining storage space designated to store ECC information (e.g., parity bits) associated with a predefined ECC algorithm utilized to encode the user data. When a bit errors associated with the user data reaches a predefined threshold value, the storage space of the flash cache may transition to store less user data so as to accommodate the space needed to store ECC information associated with a stronger ECC algorithm. The storage space of the flash cache designated to store user data is reduced, while the storage space designated to store ECC information is increased to accommodate the stronger ECC algorithm.

This application is a continuation of prior U.S. patent application Ser.No. 14/289,823 filed May 29, 2014, which is herein incorporated byreference.

FIELD

The subject matter herein relates to flash devices and, morespecifically, to a technique for adaptively strengthening errorcorrection code for a flash cache.

BACKGROUND

Due to the low costs associated with Multi-Level Cell (MLC) flashdevices, enterprise storage companies are looking for ways to switchtheir flash solutions over to MLC technology. Unfortunately, typical MLCdevices are only guaranteed for 20,000 program/erase cycles and may haveup to 36 bit errors across a 1,040-byte sector. This shorter endurancemay cause some challenges to the use of this technology in enterprisestorage products. Thus, what is needed is a technique to extend orprolong the life of a flash device, specifically a MLC flash device.

BRIEF DESCRIPTION OF THE DRAWINGS

The above and further advantages of the subject matter herein may bebetter understood by referring to the following description inconjunction with the accompanying drawings in which like referencenumerals indicate identically or functionally similar elements, ofwhich:

FIG. 1 is a schematic block diagram of storage system environment;

FIG. 2 is a schematic block diagram of a storage operating system;

FIGS. 3A and 3B are schematic block diagrams of implementations of aflash cache configured for adaptive Error Correction Code (ECC)strengthening;

FIG. 4 is schematic block diagrams of an implementation of a flash cacheconfigured for adaptive ECC strengthening;

FIGS. 5A and 5B are schematic block diagrams of implementations of aflash cache configured for adaptive ECC strengthening; and

FIG. 6 is a flowchart detailing the steps of a procedure for adaptivelystrengthening an ECC for the flash cache.

SUMMARY

The subject matter herein is directed to a technique for adaptivelystrengthening error correction code (ECC) for a flash cache (e.g., NANDflash cache) of a storage system as the flash cache ages over time andbecomes more unreliable. According to the technique, a “full” amount ofthe flash cache (e.g., storage cells) is initially utilized to storedata i.e., substantially all of the storage space of the flash cache maybe designated to store user data (e.g., data bits of a “codeword”), withthe remaining storage space designated to store ECC information (e.g.,parity bits of a “codeword”) associated with a predefined ECC algorithmutilized to encode the user data. By using the full amount of the flashcache, more user data can be stored across the storage space of thecache, thereby increasing the storage capacity (and storage service) ofthe cache, while also leveling flash wear to prolong the life of theflash cache.

In an aspect of the subject matter, a flash module may be configured tomonitor bit errors associated with the flash cache as the cache agesover time and becomes more unreliable. When the bit errors reach apredefined threshold value, the storage space of the flash cache maytransition to store less user data so as to accommodate the space neededto store additional ECC information associated with a stronger ECCalgorithm. For example, when the bit error rate (e.g., certain number ofbit errors for a predefined number of bits) monitored by the flashmodule reaches a predefined threshold value, the storage space of theflash cache designated to store user data is reduced, while the storagespace designated to store ECC information is increased to accommodatethe stronger ECC algorithm. Further, when the bit error rate of theflash cache reaches one or more next predefined threshold values, thestorage space designated to store user data may be further reduced,while the storage space designated to store ECC information is furtherincreased to accommodate a yet stronger ECC algorithm. As such, thestorage space designated to store user data gradually decreases overtime, while the storage space designated to store ECC informationincreases over time.

DETAILED DESCRIPTION

FIG. 1 is a schematic block diagram of a storage system environment 100that may be advantageously used with the subject matter describedherein. The storage system environment 100 includes a storage system120, coupled to one or more storage devices 145 of an array 160 andinterconnected with one or more clients 110 by a network 121. Thestorage system 120 may be configured to operate as part of aclient/server arrangement, as will be understood by those skilled in theart, to provide storage services to the clients 110.

In operation, the storage system 120 services data access requests(e.g., read/write requests) issued by the clients 110 over the network121. Each client 110 may be a general-purpose computer configured toexecute applications and interact with the storage system 120 inaccordance with the client/server model of information delivery. Thatis, the client may request the services of the storage system 120, andthe storage system may return the results of the services requested bythe client 110, by exchanging packets 150 over the network 121. Theclients may issue packets including file-based access protocols, such asthe Common Internet File System (CIFS) protocol or Network File System(NFS) protocol, over TCP/IP when accessing information, such as data, inthe form of data containers, such as files and directories.Alternatively, the client may issue packets including block-based accessprotocols, such as the Small Computer Systems Interface (SCSI) protocolencapsulated over TCP (iSCSI) and SCSI encapsulated over Fibre Channel(FCP), when accessing information in the form of data containers, suchas blocks or logical unit numbs (luns).

Illustratively, the storage system 120 includes a processor 122, amemory 124, a network adapter 126, a storage adapter 128, and a flashcache 130 interconnected by a system bus 125. The storage system 120also includes a storage operating system 200 that illustrativelyimplements a high-level module, such as a file system, to logicallyorganize the information as a hierarchical structure of named storagecontainers, such as directories, files, and special types of filescalled virtual disks (hereinafter “blocks”) on the disks.Illustratively, the storage operating system 200 may be implemented as aset of kernel mode processes.

The memory 124 includes memory locations that are addressable by theprocessor 122 and adapters for storing software programs and/orprocesses and data structures associated with the subject matterdiscussed herein. The processors and adapters may include processingelements and/or logic circuitry configured to execute the softwareprograms/processes and manipulate the data structures, as describedbelow. The storage operating system 200, portions of which are typicallyresident in memory and executed by the processing elements, functionallyorganizes the storage system 120 by, inter alia, invoking storageoperations executed by the storage system. It will be apparent to thoseskilled in the art that other processing and memory means, includingvarious computer readable media, may be used for storing and executingprogram instructions pertaining to the subject matter described herein.It is also expressly contemplated that the various software programs,processes and layers described herein may be embodied as modulesconfigured to operate in accordance with the disclosure, e.g., accordingto the functionality of a software program, process or layer.

The network adapter 126 comprises the mechanical, electrical andsignaling circuitry needed to connect the storage system 120 to theclient 110 over computer network 121, which may include one or morepoint-to-point connections or a shared medium, such as a local areanetwork. Illustratively, the computer network 121 may be embodied as anEthernet network or a Fibre Channel (FC) network. The client 110 maycommunicate with the storage system over network 121 by exchangingdiscrete frames or packets 150 of data according to pre-definedprotocols, such as the Transmission Control Protocol/Internet Protocol(TCP/IP).

The storage adapter 128 may cooperate with the storage operating system200 executing on the storage system 120 to access information requestedby the client 110. The information may be stored on any type of attachedarray of writable storage device media such as video tape, optical, DVD,magnetic tape, bubble memory, electronic random access memory,micro-electro mechanical and any other similar media adapted to storeinformation, including data and parity information. However, theinformation is preferably stored on disks 145, such as hard disk drives(HDDs) and/or direct access storage devices (DASDs). The storage adapter128 includes input/output (I/O) interface circuitry that couples to thedisks 145 over an I/O interconnect arrangement, such as a conventionalhigh-performance, FC serial link topology.

Storage of information on array 160 may be implemented as one or morestorage “volumes” that include a collection of physical storage disks145. The disks within a volume may be organized as one or more groups,wherein each group may be operated as a Redundant Array of Independent(or Inexpensive) Disks (RAID). Most RAID implementations enhance thereliability/integrity of data storage through the redundant writing ofdata “stripes” across a given number of physical disks in the RAIDgroup, and the appropriate storing of parity information with respect tothe striped data. An illustrative example of a RAID implementation is aRAID-4 level implementation, although it should be understood that othertypes and levels of RAID implementations may be used in accordance withthe subject matter described herein.

In an aspect of the subject matter, the flash cache 130 may be embodiedas Multi-Level Cell (MLC) NAND flash cache that includes a controller134 and a plurality of block-oriented NAND storage cells 138 coupled byan interconnect, such as bus 140. The NAND storage cells 138 may beutilize to store information (e.g., user data and ECC informationassociated with a codeword). Typically, the NAND storage cells 138 ofthe flash cache 130 may be organized as a series of blocks which aredivided into several pages. Typically, each page includes a main areaconfigured to store user data and a spare area configured to storeinformation associated with error detection and correction, etc.Further, the cells 138 of the flash cache may be organized into agranularity of one or more sectors, where a sector may be a plurality ofcells 138 on a same page, a plurality of cells 138 across differentpages of the same block, or a plurality of cells 138 across differentblocks. Although the flash storage cells are illustrativelyblock-oriented NAND cells, it will be understood to those skilled in theart that other block-oriented, nonvolatile, solid-state electronicdevices with associated storage cells or components may beadvantageously used with the subject matter described herein.

In an aspect of the subject matter, the controller 134 may be configuredto control, e.g., read and/or write access to information stored on anarray of non-volatile flash storage cells 138. For example, the flashcache 130 may be configured to store a temporary copy of user data,while a permanent copy of the data may be stored on the storage device145 coupled to the storage system 120. When a data access request (e.g.,read request) is made by the client 110, the controller 134, forexample, may serve the data from the flash cache 130, if a copy of thedata is present/available therein. The controller 134 may be configuredto execute one or more ECC algorithms 136 using a counter 132. Each ECCalgorithm 136 may be utilized to correct bit errors associated with datastored on cells 138. Specifically, the ECC algorithm 136 may includeflash correction schema, such as Forward Error Correction (FEC) codes.Further, such FEC codes may be, but are not limited to, BCH codes andLow Density Parity Check (LDPC) codes, as known by those skilled in theart. For example, prior to storing data on storage cells 138 (receivedfrom storage system 120), the ECC algorithm 136 may be utilized togenerate redundancy information (e.g., parity and/or checksum bits) forthe data. The redundancy information may then be stored with the userdata on the storage cells 138, and, for example, on the same page. Assuch, the redundancy information and the ECC algorithm 136 may beutilized to correct bit errors associated with the user data, as knownby those skilled in the art. The corrected data may then be sent to therequesting client 100.

Further, the counter 132 may be utilized to store a value associatedwith a bit error rate for user data stored on the cells 138.Illustratively, when a client 110 issues a read request for user datastored on a sector of cells 138 (e.g., a plurality of cells on the samepage), the redundancy information may be re-calculated and compared tothe redundancy information already stored on the sector of cells 138. Ifthe re-calculated redundancy information does not match the redundancydata stored on the cells 138, the controller 134 may determine thenumber of bits errors encountered for a predetermined number of bits.For example, the controller may determine, based on the comparison, thatfor every 10 bits of user data there is 1 bit that is in error (e.g.,bit error rate). As such, the counter 132 may be set to a value of 1.Alternatively, and based on the comparison, the controller 134 maydetermine the number of read requests that encountered a bit errorduring a predetermined number of read requests. For example, thecontroller 134 may determine that for every 10 read requests, 3 readrequests encountered a bit error(s). As such, the counter 132 may be setto a value of 3. As the bit error rate increases over time (and theflash cache 130 ages and becomes more unreliable), the counter 132 maybe incremented. FIG. 2 is a schematic block diagram of a storageoperating system 200 that may be advantageously used with the subjectmatter described herein. The storage operating system includes a seriesof software layers organized to form an integrated network protocolstack 202 or, more generally, a multi-protocol engine that provides datapaths for clients to access information using block and file accessprotocols. In addition, the storage operating system includes a storagestack 204 that includes storage modules that implement a storage (e.g.,RAID) protocol and manage the storage and retrieval of information toand from the flash cache 130 and array 160 in accordance with I/Ooperations. Bridging the storage stack 204 with the integrated networkprotocol stack 202 is a virtualization system that is implemented by afile system 280 that enables access by administrative interfaces, suchas a user interface (UI) 275, in response to a user (systemadministrator) issuing commands to the storage system. The UI 275 isdisposed over the storage operating system in a manner that enablesadministrative or user access to the various layers and systems.

According to the subject matter described herein, storage stack 204includes a process embodied as a flash module 285 that may, for example,cooperate with the flash cache 130 to perform operations associated withthe subject matter described herein. Specifically, the flash module 285may determine whether the bit error rate associated with the flash cache130 has reached a predefined threshold value by querying the counter 132of the flash cache 130. More specifically, the flash module 285 mayquery the counter 132 and compare the value of the counter 132 with thepredefined threshold value to determine whether the bit error rate ofthe flash cache 130 has reached the predefined threshold value. Forexample, the counter value may be 2 indicating that for every 10 bits(or another amount of bits), there are 2 bits that are in error (e.g.,bit error rate). Alternatively, the counter value of 2 may indicate thatfor a number of, e.g., 10, read operations (or another amount of readoperations), 2 read operations encountered bit errors (e.g., bit errorrate). Thereafter, the counter value of 2, indicating the bit errorrate, may be compared with the predefined threshold value that, forexample, may be set by an administrator. In this example, the predefinedthreshold value may be 2. Since the predefined threshold value has beenreached, the flash module 285 may send one or more instructions to theflash cache 130 instructing controller 134 to alter or change thedesignation of the cells 138, as described below. If the predefinedthreshold value had not been reached (e.g., counter value is 1), thenthe flash cache 130 is not instructed to alter or change the designationof the cells 138, and the flash cache 130 continues to operate.

In an aspect of the subject matter, a technique is provide thatadaptively strengthens the ECC algorithm for the flash cache 130 as theflash cache 130 ages over time and becomes more unreliable. According tothe technique, a “full” amount of the flash cache 130 (e.g., storagecells) is initially utilized to store data i.e., substantially all ofthe storage space of the flash cache may be designated to store userdata (e.g., data bits of a “codeword”), with the remaining storage spacedesignated to store ECC information (e.g., parity bits of a “codeword”)associated with a predefined ECC algorithm utilized to encode the userdata. By using the full amount of the flash cache 130, more user datacan be stored across the storage space of the cache 130, therebyincreasing the storage capacity (and storage service) of the cache 130,while also leveling flash wear to prolong the life of the flash cache130.

In an aspect of the subject matter, the flash module 285 may beconfigured to monitor the bit errors associated with the flash cache 130as the cache ages over time and becomes more unreliable. When the biterrors reach a predefined threshold value, the storage space of theflash cache 130 may transition to store less user data so as toaccommodate the space needed to store additional ECC informationassociated with a stronger ECC algorithm. For example, when the biterror rate (e.g., certain number of bit errors for a predefined numberof bits) monitored by the flash module 285 reaches a predefinedthreshold value, the storage space of the flash cache 130 designated tostore user data is reduced, while the storage space designated to storeECC information is increased to accommodate the stronger ECC algorithm.Further, when the bit error rate of the flash cache 130 reaches one ormore next predefined threshold values, the storage space designated tostore user data may be further reduced, while the storage spacedesignated to store ECC information is further increased to accommodatea yet stronger ECC algorithm. As such, the storage space designated tostore user data gradually decreases over time, while the storage spacedesignated to store ECC information increases over time.

FIGS. 3A and 3B are schematic block diagrams of implementations of theflash cache configured for adaptive ECC strengthening. Atinitialization, the storage space 302 (e.g., storage cells 138) of afirst implementation of the flash cache 130 of FIG. 3A may beapportioned into data section 305 and ECC section 310. For example,storage space 302 may be a page of the flash cache 130. Further, datasection 305 may be a sector of the page and may be the “full” amount ofstorage space, e.g., 1024-bytes, designated to store user data. The userdata stored on storage cells 138 in section 305 may be retrieved fromstorage devices 145 and subsequently provided to the client 110 inresponse to a read request. Further, ECC section 310 may be a sector ofthe page, e.g., 64-bytes, designated to store ECC information (e.g.,parity bits) associated with the user data stored in data section 305.Illustratively, an ECC algorithm 136 (e.g., BCH or LDPC) configured tosupport variable size codewords for the flash cache 130 in FIG. 3A, maybe employed to correct 36 bits scattered across the 1024-bytes of datasection 305. The flash module 285 may monitor the bit errors associatedwith the user data stored in section 305, as the flash cache 200 agesover time and becomes more unreliable. The counter 132 may be configuredto store a value associated with the bit error rate for the data storedin section 305 based on a comparison of the redundancy informationstored in section 310 and re-calculated redundancy information. When theflash module 285 determines that the bit error rate of the first flashcache implementation reaches a predefined threshold value, storage spaceof the flash cache designated to store user data may be transitioned tostore redundancy information associated with a stronger ECC algorithm.For example, the flash module 285 may determine, based on the counter132, that the bit error rate associated with the data stored in section305 reached a predefined threshold value (preconfigured by anadministrator, for example), and may then instruct the controller toalter/change the designation of the storage space, such that storagespace that was designated to store user data is lessened, while thestorage space designated to store redundancy information associated witha stronger ECC algorithm is increased.

For example, and as depicted in FIG. 3B, when the flash module 285determines that the bit error rate associated with the data stored indata section 305 of the flash cache 130 reaches a predefined thresholdvalue, the data section 305 of 1024-bytes may be split into two 512-bytedata sections 315 and 325, e.g., in accordance with a secondimplementation of the flash cache 130. Storage space that was designatedto store user data may be transitioned and designated to store the“extra” 64-bytes of ECC information to form storage space 304 of theflash cache. That is, the storage space designated to store user data isdecreased, while the storage space to store ECC information isincreased. Illustratively, the ECC section 320 may be utilized tocorrect 36 bits across the 512-bytes of data section 315, and the ECCsection 330 may be utilized to correct 36 bits across the 512-bytes ofdata section 325. Therefore, the second flash cache implementation ofFIG. 3B, which depicts storage space designated to store user datatransitioning to store ECC information, provides stronger errorcorrection than the first flash cache implementation of FIG. 3A.Further, because the ECC algorithm supports variable size codewords, anew algorithm for the flash cache implementation of FIG. 3B is notnecessary.

In an aspect of the subject matter, the ECC algorithm 136, utilized bythe flash cache implementations of FIGS. 3A and 3B, may be a layered ECCalgorithm that includes a flash correction schema (such as BCH or LDPC)with an embedded single error correcting and double error detecting(SEC-DED) code. Specifically, the SEC-DED code corrects 1-bit errors anddetects 2-bit errors across a variable size of bits, for example, a 72bit codeword. Thereafter, the results from this “first” layer of errorcorrection may be sent to the flash correction schema (i.e., “second”layer of error correction). Further, after the “first” layer of errorcorrection is performed on the data, the flash module 285 may monitorthe bit error rate associated with the results to determine whether thebit error rate associated with the user data stored on the flash cache130 reaches the predefined threshold value. Utilization of the “first”layer of error correction advantageously reduces the bit error rate,while the storage space designated to store user data may betransitioned to store ECC information at later point in time.

FIGS. 4 is a schematic block diagrams of an implementation of the flashcache configured for adaptive ECC strengthening the ECC for a flashcache 130. As known by those skilled in the art, the page organizationwithin NAND memory creates size constraints between the user data andECC information. It may be desirable for all information, i.e., the userdata and the ECC information, to be present in a single flash page inorder to minimize access latency. Further, and as known by those skilledin the art, the error correction schemas that are employed are typicallydirected to correcting a worst case number of bit errors, which occursinfrequently. Accordingly, a single page 402 of the flash cache 130 maystore user data in data section 405 and store ECC information associatedwith a ECC algorithm in section 410. When the flash module 285determines that the bit error rate associated with the user data storedin data section 405 reaches the predefined threshold value, a section415 of a different page 404 of the flash cache 130 may be designated tostore EEC information associated with a stronger ECC algorithm, forcorrecting the worst case scenario of bit errors. Access to thisdifferent page may be necessary in the infrequent case in which the ECCinformation stored in section 410 is not able to correct the user datastored in data section 405. Advantageously, the organization of the page402 and the layout of the information on the page 402 does not have tobe altered to accommodate the ECC information associated with thestronger ECC algorithm.

FIGS. 5A and 5B are schematic block diagrams of implementations of theflash cache configured for adaptive ECC strengthening. As known by thoseskilled in the art, most MLC NAND flash memories have four possiblestates per cell, such that each cell may store two bits of information.As shown in FIG. 5A, each cell 502 of a page 503 of the flash cache 130may store 2 bits, e.g., B1 and B2. The flash module 285 may monitor theunreliability (bit error rate) associated with the cells 502 as theflash cache ages over time utilizing the counter 132. Illustratively,the counter 132 may store a value of 2 indicating that for every 10 bitsof data in the page 503, 2 bits are in error. When the bit error ratereaches the predefined threshold value, the cells 502 of the page 503are transitioned to store a single bit. In this example, the predefinedthreshold value may be 1, and the flash module 285 may compare thecounter value of 2 with the predefined threshold value of 1. Thus, theflash module 285 may determine that the bit error rate has reached thepredefined threshold value and may cause the controller to alter orchange the designations of the cells of the page 503. As shown in FIG.5B, each cell 505 of the page of 506 of the flash cache 130 may nowstore 1 bit, e.g., B1, in response to the flash module 285 determiningthat the bit error rate has reached the predefined threshold value. Assuch, the MLC NAND flash memory functions as a single level cell (SLC)device when the flash module 285 determines that the bit error rate ofthe cell reaches the predefined threshold value. Therefore, the cells ofpage 506 (as depicted in FIG. 5B) function as SLC devices and have anerror rate that is less than the cells of page 503 (as depicted FIG. 5A)that function as MLC devices. Thus, although the error rate improves,the storage capacity of the cell decreases.

FIG. 6 is a flowchart detailing the steps of a procedure 600 foradaptively strengthening the ECC for a flash cache in accordance withthe subject matter described herein. The procedure 600 starts at step605 and continues to step 610, where a “full” amount of storage space ofthe flash cache is utilized to store user data. For example,substantially all of the storage space (e.g., storage cells 138) of theflash cache may be designated to store user data, while a small portionof the storage space may be designated to store ECC information forerror correction. By using the full amount of the flash cache, more userdata can be stored across the storage space of the cache, therebyincreasing the storage capacity (and storage service) of the cache,while also leveling flash wear to prolong the life of the flash cache.At step 615, the bit error rate associated with user data stored theflash cache is monitored. For example, the flash module may monitor thebit error rate as the flash cache ages over time and becomes moreunreliable. At step 620, a determination is made as to whether the biterror rate of the flash cache reaches a predefined threshold value.Illustratively, the value of the counter 132 may be compared with apredefined threshold value. If at step 620, it is determined that thebit error rate of the flash cache has not reached the predefinedthreshold value, the procedure branches to step 625 and the flash cachecontinues to operate with the same amount of storage space designated tostore user data and the same amount of storage space designated to storeECC information. If at step 620, it is determined that the bit errorrate of the flash cache has reached the predefined threshold value, theprocedure branches to step 630 and storage space designated to storeuser data is transitioned to store ECC information associated with astronger ECC algorithm. Further, if the bit error rate of the flashcache reaches a second predefined threshold value, additional storagespace designated to store user data may be transitioned and designatedto store ECC information associated with a yet stronger ECC algorithm.At step 635, the procedure ends.

The foregoing description has been directed to specific subject matter.It will be apparent, however, that other variations and modificationsmay be made to the described subject matter, with the attainment of someor all of its advantages. It is expressly contemplated that theprocedures, processes, and methods described herein may be implementedin alternative orders. For example, although reference is madetransitioning storage space of a page of the flash cache, differentgranularities may be utilized. Specifically, the subject matterdescribed herein may be applied to sectors of a page, multiple pages, ora block of the flash cache. Accordingly this description is to be takenonly by way of example and not to otherwise limit the scope of thesubject matter described herein. Therefore, it is the object of theappended claims to cover all such variations and modifications as comewithin the true spirit and scope of the subject matter.

1. A non-transitory machine readable medium having stored thereoninstructions for performing a method comprising machine executable codewhich when executed by at least one machine, causes the machine to:apportion a solid state device having storage space into two sections, afirst section of the storage space configured to store user data and asecond section of the storage space configured to store redundancyinformation for the user data; determine a bit error rate associatedwith user data stored on the solid state device; and increase thestorage space of the second section configured to store the redundancyinformation and decrease the storage space of the first sectionconfigured to store the user data, when the determined bit error rateassociated with the user data has reached a predefined threshold.
 2. Thenon-transitory machine readable medium as set forth in claim 1, whereinthe machine executable code when executed by the machine further causesthe machine to increase the second section by a first amount anddecrease the first section by the first amount.
 3. The non-transitorymachine readable medium as set forth in claim 1, wherein the redundancyinformation, stored in the second section prior to increasing thestorage space of the second section, is associated with a first errorcorrection code algorithm.
 4. The non-transitory machine readable mediumas set forth in claim 3, wherein the redundancy information, stored inthe second section after increasing the storage space of the secondsection, is associated with a second error correction code algorithmthat is stronger than the first error correction algorithm.
 5. Thenon-transitory machine readable medium as set forth in claim 1, whereinthe machine executable code when executed by the machine further causesthe machine to increase the storage space of the second section by afurther amount and decrease the storage space of the second section bythe further amount, when the determined bit error rate associated withthe user data has increased and reached a different predefinedthreshold.
 6. The non-transitory machine readable medium as set forth inclaim 1, wherein the solid state device is a multi-level cell (MLC) NANDsolid state cache.
 7. The non-transitory machine readable medium as setforth in claim 6, wherein the first section and second section togetherdefine a page of the MLC NAND solid state cache.
 8. The non-transitorymachine readable medium as set forth in claim 1, wherein the machineexecutable code when executed by the machine further causes the machineto allocate a third section of storage space of the solid state deviceto store the redundancy data, when the determined bit error rateassociated with the user data has increased and reached a differentpredefined threshold, wherein the first section and the second sectiontogether define a first page of the solid state device and the thirdsection is part of a different page of the solid state device.
 9. Amethod comprising: apportioning, by a computing device, a solid statedevice having storage space including cells into two sections, a firstsection of the storage space configured to store user data and a secondsection of the storage space configured to store redundancy informationfor the user data, where each cell of the two sections stores a firstnumber of bits; and determining, by the computing device, whether a biterror rate associated with user data stored on the solid state devicehas reached a predefined threshold, and the process further executableto change each cell of the two section to store a second number of bitsthat is less than the first number of bits, in response to determiningthat the bit error rate associated with the user data has reached apredefined threshold.
 10. The method of claim 9, wherein the redundancyinformation, is associated with an error correction code algorithm. 11.The method of claim 9, wherein the first number of bits is 2, andwherein the second number of bits is
 1. 12. The method of claim 9,wherein the solid state device is a multi-level cell (MLC) NAND solidstate cache.
 13. A non-transitory machine readable medium having storedthereon instructions for performing a method comprising machineexecutable code which when executed by at least one machine, causes themachine to: apportion a solid state device having storage spaceincluding cells into two sections, a first section of the storage spaceconfigured to store user data and a second section of the storage spaceconfigured to store redundancy information for the user data, where eachcell of the two sections stores a first number of bits; determine when abit error rate associated with user data stored on the solid statedevice has reached a predefined threshold; and change each cell of thetwo section to store a second number of bits that is less than the firstnumber of bits, in response to determining that the bit error rateassociated with the user data has reached a predefined threshold. 14.The non-transitory machine readable medium as set forth in claim 13,wherein the redundancy information, is associated with an errorcorrection code algorithm.
 15. The non-transitory machine readablemedium as set forth in claim 13, wherein the first number of bits is 2,and wherein the second number of bits is
 1. 16. The non-transitorymachine readable medium as set forth in claim 13, wherein the solidstate device is a multi-level cell (MLC) NAND solid state cache.